Hi all,

I have this scenario:

* ServerOne SQL 2012 SP1 /Reporting service (install & funcionality ok)

* ServerTwo SCOM2012SP1 (Rol to install; Management server, Operation console, Web Console, Reporting server)

When I trate to install SCOM 2012SP1 in ServerTwo, the all in the SQL server instance for reporting services not appears nothing....

For us information, the servers it's in the same network, the same domain, the firewalls it's down, the Collation it's Latin1_General_CP1_CI_AS, I can view the http://serverone/reports and http://serverone/reportserver, in other server with the user admin to SQL repoting service.

It' a BUG to the SCOM 2012 SP1 or it's a bug to SQL 2012 SP1??????

I will apreciate someone could say me what I need to do to resolve this issue.

Best regards.

Roberto Velez

Hi Roberto.

I suggest you use the following Technet article to verify that your reporting services are set up correctly, then try the install again:

http://technet.microsoft.com/en-us/library/hh298611.aspx

Best regards,

Pl Hymork.

Thanks Pal,

Thanks for the suggestion but I dont found a practice solves.

I take  another way, and install the Reporting Server in Serverone, I perish a practical solution, I guess Microsoft will have to patch in the future SP2... 

Thanks all.

Hi, that's because ServerTwo doesnt have SSRS locally installed.

http://blogs.catapultsystems.com/cfuller/archive/2012/06/25/opsmgr-2012-installation-in-a-two-server-configuration-scom-sysctr.aspx

You might want to check this post, I had the exact same issues with SQL 2012 SP1 and OpsMgr 2012 SP1 on Server 2012 SP1 which was resolved by a NIC setting (if ESX use E1000E NIC) and if Hyper-V or ESX, enabling the DisableLoopbackCheck in the registry for all Virtual Servers.  I haven't seen this apply to physical hosts yet.

http://blogs.catapultsystems.com/jcowan/archive/2013/03/21/needles-in-a-haystack-disableloopbackcheck-failed-installation-of-opsmgr-2012-sp1-databases-and-reporting-with-server-2012-and-sql-2012-sp1-over-hyper-v-and-esx-5-1-e1000e-vs-vmxnet3-networking.aspx

Just FYI, I had same difficulty. My current logged in account didn't have permission to the SQL instance. 

Solution for me was to add the current logged in account to the SQL instance under "Security\Logins" | New Login.